-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: ansible kinesis stream paginated shards bug #93
fix: ansible kinesis stream paginated shards bug #93
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sidpatel13
Thanks for taking the time to submit the issue and this patch.
I think this change might work, we currently have a pending PR to add some integration tests for kinesis_stream ( #42 ) that I'd like to get in place before we merge this.
In the mean time if possible please would you add a changelog fragment to your PR: https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to
Given the number of shards required to trigger this I'm not sure we can practically test this properly without delving into the realms of unit tests and I'm not a big fan of unit tests for modules so I'm inclined to wave that requirement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I'm going to wait on getting the integration tests in place before merging.
@sidpatel13 this PR contains the following merge commits: Please rebase your branch to remove these commits. |
add42b2
to
d1e64de
Compare
@ansibullbot rebased! |
@tremble @ansibullbot any updates on when this will get merged? |
Sorry it took so long, We've got the initial test suite in now and I've triggered a run. I'll manually run through the results (there are some known bugs) and then we can get this merged. |
Sorry this took so long to get merged. |
…ansible-collections#93) * ec2_ami - Ensure suboptions in docs match what's parsed and validated * Use 2.6 compatible mecahism for removing None entries.
SUMMARY
"Fixes #92"
It looks like
has_more_shards
isn't really used other than for the purposes of this while loop so it is safe to setExclusiveStartShardId
to the last shard and pass those params at the next call of the while loop which subsequently setshas_more_shards
to False. Otherwise, due to a kinesis stream having > 100 shards,has_more_shards
will always be True making us stuck in this while loop and we'll get timeouts.ISSUE TYPE